adjust lv3 blotting functionality#173
Merged
akleroy merged 1 commit intoPhangsTeam:mainfrom Apr 3, 2026
Merged
Conversation
akleroy
approved these changes
Apr 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rather than blotting the drizzled frames back to the detector coordinates of a reference exposure, we now blot the i2d mosaic to the detector frame of individual exposures. See
docs/steps/lv3.rstfor documentation and examples of how to use this.End to end run on a MIRI observations for one target ran successfully (I set
do_blot=Trueanddo_drizzle=Trueand inspected outputs).cc @akleroy